System and method for providing a spend memory record

ABSTRACT

Systems and methods include a database maintained by a financial institution that stores transaction data associated with a previous financial transaction performed via a financial account of a respective account holder, wherein the transaction data comprises a transaction location and a transaction timestamp, a spend memory processor of the financial institution that retrieves the transaction data from the database, interacts with a social linking application programming interface (API) to receive, via a network, social data from a social networking site, wherein the social data comprises a social location and a social timestamp, compares the social data to the transaction data, and creates a spend memory record based on one or more similarities between the social data and the transaction data, and a communication interface of the financial institution that provides the spend memory record to a mobile device associated with the account holder.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of, and claims priority under 35U.S.C. § 120 to, U.S. patent application Ser. No. 14/856,940, filed Sep.17, 2015, of the same title (the '940 Application). The '940Application, in turn, claims benefit of, and priority under 35 U.S.C. §119(e) to, U.S. Provisional Patent Application No. 62/051,398, filed onSep. 17, 2014, of the same title. The entire contents of bothapplications are hereby incorporated by reference.

This application contains subject matter related to U.S. patentapplication Ser. No. 14/168,107, filed on Jan. 30, 2014, and U.S. patentapplication Ser. No. 14/031,263, filed on Sep. 19, 2013, the entirecontents of which are incorporated herein by reference.

FIELD OF THE DISCLOSURE

The present disclosure relates to systems and methods for providing afinancial statement that includes memory-enhancing information toprovide social context for a user's transaction history.

BACKGROUND OF THE DISCLOSURE

Currently, a user's financial statement (e.g., a credit card statement)provides a list of purchases made during that month without much, ifany, additional context. A user may have been on a trip and mademultiple purchases while taking photos around the same time. Thefinancial statement may not reflect the user's social activities thatcoincided with the purchases reflected on the statement. The user maynot remember which transactions are associated with which social events.

These and other drawbacks exist.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments of the present disclosure, together with furtherobjects and advantages, may best be understood by reference to thefollowing description taken in conjunction with the accompanyingdrawings, in the several Figures of which like reference numeralsidentify like elements, and in which:

FIG. 1 depicts a schematic diagram of a system for providing a spendmemory record to an account holder at his or her mobile device accordingto an example embodiment of the disclosure;

FIG. 2 depicts a schematic diagram of a point of sale system that may beassociated with providing a spend memory record to an account holder athis or her mobile device according to an example embodiment of thedisclosure;

FIG. 3 depicts a schematic diagram of a system for providing a spendmemory record to an account holder at his or her mobile device accordingto an example embodiment of the disclosure;

FIG. 4 depicts a schematic diagram of a method for providing a spendmemory record to an account holder at his or her mobile device accordingto an example embodiment of the disclosure; and

FIGS. 5A-5B depict screenshots of a spend memory record on a mobiledevice, according to an example embodiment of the disclosure.

DETAILED DESCRIPTION OF THE EMBODIMENTS

The following description is intended to convey a thorough understandingof the embodiments described by providing a number of specific exampleembodiments and details involving systems and methods for providing afinancial statement that includes memory-enhancing information toprovide social context for a user's transaction history. It should beappreciated, however, that the present disclosure is not limited tothese specific embodiments and details, which are examples only. It isfurther understood that one possessing ordinary skill in the art, inlight of known systems and methods, would appreciate the use of thedisclosure for its intended purposes and benefits in any number ofalternative embodiments, depending on specific design and other needs. Afinancial institution and system supporting a financial institution areused as examples for the disclosure. The disclosure is not intended tobe limited to financial institutions only.

In an example embodiment, a user having a financial account at afinancial institution may make one or more purchases. Around the sametime, the user may upload data to a mobile device via, for example, asocial media account (e.g., photos, status updates). The social data maybe geotagged and include a timestamp. For example, a user device maygeotag a photo to include location data indicating the location wherethe photo was taken. In various embodiments, the social networking sitethat supports the social media account may geotag the photo when theuser device uploads the photo to the social media account. Thetransaction data for the purchases may also be geotagged and include atimestamp. A spend memory processor may receive the transaction data ona regular basis. The spend memory processor may also retrieve and/orutilize social data from the user's social media account. In variousembodiments, the spend memory processor may also retrieve and/or utilizelocal data from the user's mobile device (e.g., photos, phone callrecords). The spend memory processor may compare the transaction data tothe social data and/or local data and create an enhanced financialstatement (a “spend memory record”) that links social data and localdata with transaction data based on similarities in the timestamps,location data, and other relevant information. For example, if a photofrom the user's social media account was geotagged to indicate it wastaken on Aug. 20, 2014 at 2:30 PM at Pier 39 in San Francisco, Calif.,and the user's transaction data indicates that the user bought lunch atPier 39 on Aug. 20, 2014 at 12:30 PM, the spend memory processor maycreate a spend memory record that includes the transaction data for thecoffee purchase and the photo, based on relative similarities betweenthe location data and timestamps.

FIG. 1 depicts an example embodiment of a system for providing a spendmemory record that includes information to provide social context for auser's transaction history, according to various embodiments of thedisclosure. As referred to herein, a “spend memory record” may include,for example, an interactive, feature-rich purchase history associatedwith a user account (e.g., a credit and/or debit account) as shown anddescribed herein. Referring to FIG. 1, the system may include variousnetwork-enabled computer systems, including, as depicted in FIG. 1 forexample, a financial institution 101; comprising a spend memoryprocessor 104, and an account database 106, which may be included asseparate processors or combined into a single processor or device havingthe multiple processors. The system may also include a social networkingsite 110. Examples of social networking sites include, withoutlimitation, Instagram, Facebook, MySpace, Google+, LinkedIn, Twitter,Pintrest, etc. The social networking site may include a plurality ofsocial networking accounts created by one or more users. The users mayalso be account holders with the financial institution 101.

In various examples, the spend memory processor 104 and/or database 105may be separate from financial institution 101. For example, spendmemory processor 104 may be integrated into social networking site 110.Social networking site 110, merchant 109, and spend memory processor 104may comprise one or more network-enabled computers. As referred toherein, a network-enabled computer system and/or device may include, butis not limited to: e.g., any computer device, or communications deviceincluding, e.g., a server, a network appliance, a personal computer(PC), a workstation, a mobile device, a phone, a handheld PC, a personaldigital assistant (PDA), a thin client, a fat client, an Internetbrowser, or other device. The network-enabled computer systems mayexecute one or more software applications to, for example, receive dataas input from an entity accessing the network-enabled computer system,process received data, transmit data over a network, and receive dataover a network. The one or more network-enabled computer systems mayalso include one or more software applications to enable the creationand provisioning of spend memory statements.

The components depicted in FIG. 1 may store information in variouselectronic storage media, such as, for example, account database 106 andtransaction database 107. Electronic information, files, and documentsmay be stored in various ways, including, for example, a flat file,indexed file, hierarchical database, relational database, such as adatabase created and maintained with software from, for example, Oracle®Corporation, Microsoft® Excel file, Microsoft® Access file, or any otherstorage mechanism.

The components depicted in FIG. 1 may be coupled via one or morenetworks, such as, for example, network 108. Network 108 may be one ormore of a wireless network, a wired network or any combination ofwireless network and wired network. For example, network 108 may includeone or more of a fiber optics network, a passive optical network, acable network, an Internet network, a satellite network, a wireless LAN,a Global System for Mobile Communication (“GSM”), a PersonalCommunication Service (“PCS”), a Personal Area Network (“PAN”), D-AMPS,Wi-Fi, Fixed Wireless Data, IEEE 802.11b, 802.15.1, 802.11n and 802.11gor any other wired or wireless network for transmitting and receiving adata signal.

In addition, network 108 may include, without limitation, telephonelines, fiber optics, IEEE Ethernet 902.3, a wide area network (“WAN”), alocal area network (“LAN”), or a global network such as the Internet.Also network 108 may support an Internet network, a wirelesscommunication network, a cellular network, or the like, or anycombination thereof. Network 108 may further include one network, or anynumber of the example types of networks mentioned above, operating as astand-alone network or in cooperation with each other. Network 108 mayutilize one or more protocols of one or more network elements to whichthey are communicatively coupled. Network 108 may translate to or fromother protocols to one or more protocols of network devices. Althoughnetwork 108 is depicted as a single network, it should be appreciatedthat according to one or more embodiments, network 108 may comprise aplurality of interconnected networks, such as, for example, theInternet, a service provider's network, a cable television network,corporate networks, and home networks.

In various example embodiments, an account holder may be any individualor entity that desires to conduct a financial transaction using one ormore accounts held at one or more financial institutions. An account mayinclude any place, location, object, entity, or other mechanism forholding money or performing transactions in any form, including, withoutlimitation, electronic form. An account may be, for example, a creditcard account, a prepaid card account, stored value card account, debitcard account, check card account, payroll card account, gift cardaccount, prepaid credit card account, charge card account, checkingaccount, rewards account, line of credit account, credit account, mobiledevice account, an account or service that links to an underlyingpayment account already described, or mobile commerce account. Anaccount may or may not have an associated card, such as, for example, acredit card for a credit account or a debit card for a debit account.The account may enable payment using biometric authentication, orcontactless based forms of authentication, such as QR codes ornear-field communications. The account card may be associated oraffiliated with one or more social networking sites, such as aco-branded credit card.

User device 102 may be, for example, a handheld PC, a phone, asmartphone, a PDA, a tablet computer, or other device. User device 102may include an iPhone, iPod, iPad from Apple® or any other mobile devicerunning Apple's iOS operating system, any device running Google'sAndroid® operating system, including for example, Google's wearabledevice, Google Glass, any device running Microsoft's Windows® Mobileoperating system, and/or any other smartphone or like wearable mobiledevice. Device 102 may include device-to-device communication abilitiesusing, for example, RFID transmitters and receivers, cameras, scanners,and/or Near Field Communication (NFC) capabilities, which may allow forcommunication with other devices by touching them together or bringingthem into close proximity. Example NFC standards include ISO/IEC18092:2004, which defines communication modes for Near FieldCommunication Interface and Protocol (NFCIP-1). For example, device 102may be configured using the Isis Mobile Wallet™ system, which isincorporated herein by reference. Other exemplary NFC standards includethose created by the NFC Forum. Element 102 c may use Bluetoothtechnology built into device 102. Element 102 c may use iBeacontechnology and/or Bluetooth Low Energy (BLE) capabilities.

A financial institution 101 may be, for example, a bank, other type offinancial institution, including a credit card provider, for example, orany other entity that offers accounts to customers. Financialinstitution 101 may have one or more databases 106 comprisinginformation about an account holder's accounts.

The user of user device 102 may have a mobile banking application 103 onuser device 102. Mobile banking application 103 may allow the user toaccess his accounts with financial institution 101. The accounts may beassociated with a username and password. Upon logging in for mobilebanking application 103, the user may be presented with a “spend memory”option. If the user selects the “spend memory” option, the user may bepresented with a request to link his social media accounts (with socialnetworking site 110) to his one or more financial accounts withfinancial institution 101. The user may provide a username and passwordassociated with his one or more social media accounts at socialnetworking site 110 (i.e., the identifying information that is needed toaccess the social media accounts). The user may use mobile bankingapplication 103 to create a set of permissions associated with his oneor more social media accounts. The set of permissions may include thetypes of social data that spend memory processor 104 can collect fromthe user's social media accounts. Social data may include photos andvideos that the user posts to his social media accounts. Social data caninclude tweets, pins, tags, check-ins, likes, status updates, comments,profile information, posts, and other information. The set ofpermissions may allow spend memory processor to retrieve certain typesof social data (e.g., photos) and not others (e.g., no status updates orcomments).

Social networking site 110 may create a hashcode based on the user'sidentifying information and the set of permissions. Social networkingsite 110 may provide the hashcode as a token to spend memory processorvia a social application programming interface (API) 111. Spend memoryprocessor 104 may associated the token with accounts for the user ofuser device 102 (for example, by storing the token in account database106). The token may include the set of permissions provided by the userof user device 102. Spend memory processor 104 may regularly requestsocial data from social networking site 110. Each time spend memoryprocessor 104 requests new social data, the request will include thetoken. Social networking site 110 may provide new social data to spendmemory processor 104 based on the set of permissions associated with thetoken. Spend memory processor may receive the social data associatedwith the user and save it with the user's account information in accountdatabase 106.

The “spend memory” feature may also include an option to permit spendmemory processor 104 to periodically access and/or retrieve local datafrom user device 102. Local data may include, for example, photos andvideos that the user took that are stored on user device 102. Local datamay include call logs (i.e., a list of incoming and outgoing callsand/or text messages). The social data and/or the local data may includea timestamp (indicating the date and time at which the data wascreated). The social data and/or local data may be geotagged at the timeit is created (e.g., by user device 102, social networking site 110,network 108, or by a third party). Data that is geotagged includeslocation data indicating the current location of user device 102 at thetime the data was created and/or uploaded. In various exampleembodiments, various location services on user device 102 may be used todetermine the device's current location. For example, user device 102may use information from cellular, Wi-Fi, Global Positioning System(GPS) networks and/or iBeacons or other similar devices to determine anapproximate location. User device 102 may, for example, periodicallysend the geo-tagged location of nearby Wi-Fi hotspots and cell towers inan anonymous and/or encrypted form to an aggregator that may improvelocation accuracy. Where, for example, the mobile device is an Appledevice (e.g., an iPhone, iPad, iPod, smart watch, etc.) the CoreLocation framework may be used to receive and monitor the currentlocation of the mobile device. For example, a mobile banking applicationmay link to Core Location framework in an Xcode project to enable themobile banking application to locate the current position of the device.Where for example, the mobile device is running the Google Androidplatform, the ACCESS COARSE LOCATION and FINE strings may be used by themobile banking application to obtain the location of the mobile device.

The user of user device 102 may make a series of purchases with merchant109 using his account with financial institution 101. The purchases maybe made at a Point of Sale (PoS) terminal associated with merchant 109(such as PoS device 200 as shown in FIG. 2). Merchant 109, financialinstitution 101, and/or a third-party may create transaction data basedon each purchase. The transaction data may be stored in transactiondatabase 107 by the merchant 109 once the transaction is completed.Spend memory processor 104 may receive the transaction data fromtransaction database 107 via transaction API 105. The transaction datamay include meta-data information such as a timestamp indicating thedate and time of the transaction, the transaction amount, a merchantidentifier (associated with merchant 109), merchant 109's location(e.g., a physical address and/or GPS coordinates), a merchant logo, amerchant category, the last four digits of the card used for thetransaction, etc. Referring back to FIG. 1, spend memory processor 104may be configured to receive transaction data via network 108 and/or aseparate network (not shown). The transaction data may be associatedwith a financial transaction performed by the account holder at merchant109 using user device 102. The account holder may perform thetransaction using one or more mobile payment accounts associated withuser device 102. The account holder may purchase one or more goods orservices at merchant 109, and the resulting expenses may be chargedagainst the account holder's mobile payment account.

Spend memory processor 104 may store the transaction data in accountdatabase 106. The transaction data may be received on an hourly, daily,weekly, monthly, or other regular basis. Spend memory processor 104 mayrequest the transaction data from transaction database 107 at irregularintervals. Spend memory processor 104 may request transaction data for auser each time the user logs in to mobile banking application 103.

Spend memory processor 104 may compare a user's transaction data withsocial data and local data received from social networking site 110and/or user device 102. Spend memory processor 104 may compare thetimestamp and location data associated with a transaction (transactionlocation data and transaction timestamp data) with timestamp andlocation data associated with the social data and local data (sociallocation data and social timestamp data) received from social networkingsite 110 and/or user device 102. Spend memory processor 104 may generatean enhanced transaction record (“spend memory statement”) based on oneor more matches between the transaction location data and transactiontimestamp data with the social location data and social timestamp data.The spend memory statements may include photos, status updates, posts,tweets, pins, and other relevant social data next to transaction recordsto provide context for each transaction.

Spend memory processor 104 may match transaction location data withsocial location data based on one or more location thresholds. Thelocation threshold may indicate a match based on the distance betweenthe transaction location data and the social location data (e.g., within100 yards, 1 mile, 5 miles, etc.). The location threshold may indicate amatch based on the proximity between the transaction location data andthe social location data (e.g., same block, same city, same zip code,same street address, same county, same state). Spend memory processor104 may match transaction timestamp data with social timestamp databased on one or more time thresholds. The time threshold may indicate amatch based on the difference in time between the transaction timestampdata and the social timestamp data (e.g., within 1 hour, 12 hours, 1day, 1 week, etc.). Spend memory processor 104 may retrieve transactiondata for transactions that were made in-person by the user of userdevice 102. Spend memory processor 104 may determine a match betweentransaction data and social data based on one or more combinations oflocation threshold matches and timestamp threshold matches. In variousembodiments, spend memory processor 104 may apply only a locationthreshold to the comparison between the transaction data and the socialdata if the comparison meets one or more of the time thresholds, andvice versa.

In one example, a user may travel to the Outer Banks in North Carolinafor a vacation over Labor Day weekend (August 29-September 1). While onvacation, on August 30, the user may purchase gas at a station in NagsHead, N.C. and eat lunch there at a local restaurant. On the same day,the user may spend several hours at a beach near Kitty Hawk (from 2 pm-6pm), take several photos and save them on user device 102, and upload aphoto of the beach to his social media account at social networking site110. The user may also “check-in” at Kitty Hawk by uploading thislocation to his social media account at social networking site 110.Spend memory processor 104 may receive transaction data from transactiondatabase 107. The transaction data may include transaction records forthe gas station purchase and the restaurant purchase. The transactionrecords may include the transaction location data (e.g., the location ofthe gas station and restaurant as a physical address and/or GPScoordinates). The transaction records may include transaction timestampsfor each purchase. Spend memory processor 104 may receive social datafrom social networking site 110 for that user's social media account(assuming the user had previously opted-in to the spend memory service).Spend memory processor 104 may transmit a request for social data tosocial networking site 110. The request may include the hashcode thatwas previously created when the user opted-in for the spend memoryservice. Social networking site 110 may provide social data for theuser's social networking site to spend memory processor 104 based on theone or more limitations associated with the hashcode (as describedabove). Spend memory processor 104 may also receive and/or pull localdata from user device 102, such as photos, call records, videos, notes,etc.

Spend memory processor 104 may compare the social location data andsocial timestamp data with the transaction location data and transactiontimestamp data. In this example, the social location data for the“check-in” would be near Kitty Hawk, N.C. The social location data maybe GPS coordinates. The social location data for the photo uploaded tosocial networking site 110, as well as the photos stored at user device102, may be similar. The social timestamp data may show the date andtime (Aug. 30, 2014, 2:30:52 PM) for the photos and/or “check-in”. Spendmemory processor 104 may determine that the transactions occurred on thesame day as the social data. Spend memory processor 104 may apply a timethreshold of 12 hours, and determine that the transactions occurredwithin 12 hours of the social data being created and/or uploaded. Spendmemory processor 104 may apply a location threshold of 20 miles anddetermine that the social data (photos, check-in) were created and/oruploaded (in Kitty Hawk, N.C.) less than 20 miles from where thetransactions took place (in Nags Head, N.C.).

Spend memory processor 104 may create a spend memory record thatincludes the transaction data and the social data that are associatedbased on one or more matches. The spend memory record may includetransaction data for the gas station and restaurant purchases. Thetransaction data in the spend memory record may include the amountspent, an account number, the date and time, the location, the name ofthe merchant, etc. The spend memory record may include social data basedon the one or more matches described above. The spend memory record mayshow the photo of the beach at Kitty Hawk next to the transaction data.The spend memory record may include the “check-in” from the social data.The spend memory record may include text indicating that the purchaseswere made during a vacation to the Outer Banks.

Spend memory processor 104 may provide the spend memory record to userdevice 102. The spend memory record may be provided as a Graphical UserInterface (GUI). The user may access the spend memory record usingmobile banking application 103 (e.g., by selecting a link labeled “viewspend memory record for August 2014” on the interface provided by mobilebanking application 103). In various embodiments, the spend memoryrecord may include one or more interactive features that query the userto confirm whether the social data in the spend memory record wasproperly matched to the transaction data. In this way, the spend memoryrecord may be used as a fraud control mechanism for a financialinstitution. For example, the spend memory record interface couldinclude components that enable an account holder to confirm, validateand/or otherwise authorize a particular transaction.

FIGS. 5A and 5B depict an example embodiment of a spend memory record,shown on the screen of a user device. The user may access the spendmemory record using mobile banking application 103. As shown in FIG. 5A,the spend memory record 501 may list a series of transactions 502. Thetransaction data for each transaction 502 a-502 d may include the date,transaction amount, merchant identifiers, and other relevantinformation. The spend memory may include an interactive feature 503 a,503 b allowing the user to “view spend memory” 503 a, 503 b informationfor each transaction (if spend memory information is available). If theuser selects the “view spend memory” option for a specific transaction(or transactions), mobile banking application 103 may display the screenshown in FIG. 5B. In FIG. 5B, the spend memory record 511 may show thetransaction data for that specific date (or dates). In this example, thedate is Jun. 28, 2014, and the transaction was at a Target in MyrtleBeach, S.C. The spend memory record may show social data that wasassociated with the transaction by spend memory processor 104 (based onone or more matches as described above). In this example, the socialdata includes a photo 512 and “check in” status 513 from Myrtle Beach,S.C. The user may view this spend memory record, or select other spendmemory records associated with other transactions (from FIG. 5A).

FIG. 2 depicts an example Point of Sale (PoS) device 200. PoS device 200may provide the interface at what a customer or end user makes a paymentto the merchant in exchange for goods or services. The PoS device 200may provide the transaction data to the merchant and/or a third-partyprocessor and/or transaction database 107. In various embodiments,numerous features described with respect to PoS device 200 may beimplemented into mobile banking application executing on a mobile device(e.g., client device 202).

PoS device 200 may include and/or cooperate with weighing scales,scanners, electronic and manual cash registers, electronic fundstransfer at point of sale (EFTPOS) terminals, touch screens and anyother wide variety of hardware and software available for use with PoSdevice 200. PoS device 200 may be a retail point of sale system and mayinclude a cash register and/or cash register-like computer components toenable purchase transactions. PoS device 200 also may be a hospitalitypoint of sale system and include computerized systems incorporatingregisters, computers and peripheral equipment, usually on a computernetwork to be used in restaurant, hair salons, hotels or the like. PoSdevice 200 may be a wireless point of sale device similar to a PoSdevice described herein or, for example a tablet computer that isconfigured to operate as a PoS device, including for example, softwareto cause the tablet computer to execute point of sale functionality anda card reader such as for example the Capital One® SparkPay card reader,the Square® reader, Intuit's® GoPayment reader, or the like. PoS device200 also may be a cloud-based point of sale system that can be deployedas software as a service, which can be accessed directly from theInternet using, for example, an Internet browser.

Referring to FIG. 2, an example PoS device 200 is shown. PoS device 200may include a controller 202, a reader interface 204, a data interface206, a smartcard reader 208, a magnetic stripe reader 210, a near-fieldcommunications (NFC) reader 212, a power manager 214, a keypad 216, anaudio interface 218, a touchscreen/display controller 220, and a display222. Also, PoS device 200 may be coupled with, integrated into orotherwise connected with a cash register/retail enterprise system 224.

In various embodiments, Controller 202 may be any controller orprocessor capable of controlling the operations of PoS device 200. Forexample, controller 202 may be an Intel® 2nd Generation Core™ i3 or i5or Pentium™ G850 processor or the like. Controller 202 also may be acontroller included in a personal computer, smartphone device, tablet PCor the like.

Reader interface 204 may provide an interface between the various readerdevices associated with PoS device 200 and PoS device 200. For example,reader interface 204 may provide an interface between smartcard reader208, magnetic stripe reader 210, NFC reader 212 and controller 202. Invarious embodiments, reader interface 204 may be a wired interface suchas a USB, RS222 or RS485 interface and the like. Reader interface 204also may be a wireless interface and implement technologies such asBluetooth, the 802.11(x) wireless specifications and the like. Readerinterface 204 may enable communication of information read by thevarious reader devices from the various reader devices to PoS device 200to enable transactions. For example, reader interface 204 may enablecommunication of a credit or debit card number read by a reader devicefrom that device to PoS device 200. In various embodiments, readerinterface 204 may interface between PoS device 200 and other devicesthat do not necessarily “read” information but instead receiveinformation from other devices.

Data interface 206 may allow PoS device 200 to pass communicate datathroughout PoS device and with other devices including, for example,cash register/retail enterprise system 224. Data interface 206 mayenable PoS device 200 to integrate with various customer resourcemanagement (CRM) and/or enterprise resource management (ERP) systems.Data interface 206 may include hardware, firmware and software that makeaspects of data interface 206 a wired interface. Data interface 206 alsomay include hardware, firmware and software that make aspects of datainterface 206 a wireless interface. In various embodiments, datainterface 206 also enables communication between PoS device otherdevices.

Smartcard reader 208 may be any electronic data input device that readsdata from a smart card. Smartcard reader 208 may be capable of supplyingan integrated circuit on the smart card with electricity andcommunicating with the smart card via protocols, thereby enabling readand write functions. In various embodiments, smartcard reader 208 mayenable reading from contact or contactless smart cards. Smartcard reader208 also may communicate using standard protocols including ISO/IEC7816, ISO/IEC 14443 and/or the like or proprietary protocols.

Magnetic stripe reader 210 may be any electronic data input device thatreads data from a magnetic stripe on a credit or debit card, forexample. In various embodiments, magnetic stripe reader 210 may includea magnetic reading head capable of reading information from a magneticstripe. Magnetic stripe reader 210 may be capable of reading, forexample, cardholder information from tracks 1, 2, and 3 on magneticcards. In various embodiments, track 1 may be written on a card withcode known as DEC SIXBIT plus odd parity and the information on track 1may be contained in several formats (e.g., format A, which may bereserved for proprietary use of the card issuer; format B; format C-Mwhich may be reserved for us by ANSI subcommittee X3B10; and format N-Z,which may be available for use by individual card issuers). In variousembodiments, track 2 may be written with a 5-bit scheme (4 data bitsplus 1 parity). Track 3 may be unused on the magnetic stripe. In variousembodiments, track 3 transmission channels may be used for transmittingdynamic data packet information to further enable enhanced token-basedpayments. Track 3 transmission channels also may be used to transmit,for example, geolocation data associated with a user, product datarelating to the purchase (e.g., product information, stock keeping unit(SKU) level data, and/or any other information that may be used toprovide purchase-driven smart statements. PoS device 200 may communicateand or cooperate with the user device to provide the information intotrack 3 transmission channels. Other methods for providing product leveldata to a financial institution. For example, a merchant can transmitthe product data for each transaction to a financial institution alongwith information that identifies the transaction.

NFC reader 212 may be any electronic data input device that reads datafrom an NFC device. In an exemplary embodiment, NFC reader 212 mayenable Industry Standard NFC Payment Transmission. For example, the NFCreader 212 may communicate with an NFC enabled device to enable two loopantennas to form an air-core transformer when placed near one another byusing magnetic induction. NFC reader 212 may operate at 13.56 MHz or anyother acceptable frequency. Also, NFC reader 212 may enable a passivecommunication mode, where an initiator device provides a carrier field,permitting answers by the target device via modulation of existingfields. Additionally, NFC reader 212 also may enable an activecommunication mode by allowing alternate field generation by theinitiator and target devices.

In various embodiments, NFC reader 212 may deactivate an RF field whileawaiting data. NFC reader 212 may receive communications containingMiller-type coding with varying modulations, including 100% modulation.NFC reader 212 also may receive communications containing Manchestercoding with varying modulations, including a modulation ratio ofapproximately 10%, for example. Additionally, NFC reader 212 may becapable of receiving and transmitting data at the same time, as well aschecking for potential collisions when the transmitted signal andreceived signal frequencies differ.

NFC reader 212 may be capable of utilizing standardized transmissionprotocols, for example but not by way of limitation, ISO/IEC 14443 A/B,ISO/IEC 18092, MiFare, FeliCa, tag/smartcard emulation, and the like.Also, NFC reader 212 may be able to utilize transmission protocols andmethods that are developed in the future using other frequencies ormodes of transmission. NFC reader 212 also may be backwards-compatiblewith existing payment techniques, such as, for example RFID. Also, NFCreader 212 may support transmission requirements to meet new andevolving payment standards including internet-based transmissiontriggered by NFC. In various embodiments, NFC reader 212 may utilizeMasterCard's® PayPass and/or Visa's® PayWave and/or American Express'®ExpressPay systems to enable transactions.

Although not shown and described, other input devices and/or readers,such as for example, barcode readers and the like are contemplated.

Power manager 214 may be any microcontroller or integrated circuit thatgoverns power functions of PoS device 200. Power manager 214 mayinclude, for example, firmware, software, memory, a CPU, a CPU,input/output functions, timers to measure intervals of time, as well asanalog to digital converters to measure the voltages of the main batteryor power source of PoS device 200. In various embodiments, Power manager214 remain active even when PoS device 200 is completely shut down,unused, and/or powered by the backup battery. Power manager 214 may beresponsible for coordinating many functions, including, for example,monitoring power connections and battery charges, charging batterieswhen necessary, controlling power to other integrated circuits withinPoS device 200 and/or other peripherals and/or readers, shutting downunnecessary system components when they are left idle, controlling sleepand power functions (on and off), managing the interface for built-inkeypad and trackpads, and/or regulating a real-time clock (RTC).

Keypad 216 may any input device that includes a set of buttons arranged,for example, in a block or pad and may bear digits, symbols and/oralphabetical letters. Keypad 216 may be a hardware-based ormechanical-type keypad and/or implemented in software and displayed on,for example, a screen or touch screen to form a keypad. Keypad 216 mayreceive input from a user that pushed or otherwise activates one or morebuttons on keypad 216 to provide input.

Audio interface 218 may be any device capable of providing audio signalsfrom PoS device 200. For example, audio interface may be a speaker orspeakers that may produce audio signals. In various embodiments, audiointerface 218 may be integrated within PoS device 200. Audio interface218 also may include components that are external to PoS device 200.

Touchscreen/display control 220 may be any device or controller thatcontrols an electronic visual display. Touchscreen/display control 220may allow a user to interact with PoS device 200 through simple ormulti-touch gestures by touching a screen or display (e.g., display222). Touchscreen/display control 220 may be configured to control anynumber of touchscreens, including, for example, resistive touchscreens,surface acoustic wave touchscreens, capacitive touchscreens, surfacecapacitance touchscreens, projected capacitance touchscreens, mutualcapacitance touchscreens, self-capacitance touchscreens, infrared gridtouchscreens, infrared acrylic projection touchscreens, opticaltouchscreens, touchscreens based on dispersive signal technology,acoustic pulse recognition touchscreens, and the like. In variousembodiments, touchscreen/display control 220 may receive inputs from thetouchscreen and process the received inputs. Touchscreen/display control220 also may control the display on PoS device 200, thereby providingthe graphical user interface on a display to a user of PoS device 200.

Display 222 may be any display suitable for a PoS device. For example,display 222 may be a TFT, LCD, LED or other display. Display 222 alsomay be a touchscreen display that for example allows a user to interactwith PoS device 200 through simple or multi-touch gestures by touching ascreen or display (e.g., display 222). Display 222 may include anynumber of touchscreens, including, for example, resistive touchscreens,surface acoustic wave touchscreens, capacitive touchscreens, surfacecapacitance touchscreens, projected capacitance touchscreens, mutualcapacitance touchscreens, self-capacitance touchscreens, infrared gridtouchscreens, infrared acrylic projection touchscreens, opticaltouchscreens, touchscreens based on dispersive signal technology,acoustic pulse recognition touchscreens, and the like. In variousembodiments, 222 may receive inputs from control gestures provided by auser. Display 222 also may display images, thereby providing thegraphical user interface to a user of PoS device 200.

Cash register/retail enterprise system 224 may me any device or devicesthat cooperate with PoS device 200 to process transactions. Cashregister/retail enterprise system 224 may be coupled with othercomponents of PoS device 200 via, for example, a data interface (e.g.,data interface 206) as illustrated in FIG. 2. Cash register/retailenterprise system 224 also may be integrated into PoS device 200.

In various embodiments, cash register/retail enterprise system 224 maybe a cash register. Example cash registers may include, for example,mechanical or electronic devices that calculate and record salestransactions. Cash registers also may include a cash drawer for storingcash and may be capable of printing receipts. Cash registers also may beconnected to a network to enable payment transactions. Cash registersmay include a numerical pad, QWERTY or custom keyboard, touch screeninterface, or a combination of these input methods for a cashier toenter products and fees by hand and access information necessary tocomplete the sale.

In various embodiments, cash register/retail enterprise system 224 maycomprise a retail enterprise system and/or a customer relationshipmanagement system. Retail enterprise system 224 may enable retainenterprises to manage operations and performance across a retailoperation. Retail enterprise system 224 may be a stand-alone applicationin, for example, individual stores, or may be interconnected via anetwork. Retail enterprise system 224 may include various point of salecapabilities, including the ability to, for example, customize andresize transaction screens, work with a “touch screen” graphical userinterface, enter line items, automatically look up price (sales,quantity discount, promotional, price levels), automatically computetax, VAT, look up quantity and item attribute, display item picture,extended description, and sub-descriptions, establish default shippingservices, select shipping carrier and calculate shipping charges byweight/value, support multi-tender transactions, including cash, check,credit card, and debit card, accept food stamps, place transactions onhold and recall, perform voids and returns at POS, access online creditcard authorizations and capture electronic signatures, integrate debitand credit card processing, ensure optional credit card discounts withaddress verification, support mix-and-match pricing structure, discountentire sale or selected items at time of sale, add customer account,track customer information, including total sales, number of visits, andlast visit date. issue store credit, receive payment(s) for individualinvoices, process deposits on orders, search by customer's ship-toaddress, create and process layaway, back orders, work orders, and salesquotes, credit items sold to selected sales reps, view daily sales graphat the PoS, view and print journals from any register, preview, search,and print journals by register, batch, and/or receipt number, print X,Z, and ZZ reports, print receipts, invoices, and pick tickets withlogos/graphics, print kit components on receipt, reprint receipts, enteremployee hours with an integrated time clock function, and/or sell whenthe network/server is down with an offline PoS mode. Retail enterprisesystem 224 also may include inventory control and tracking capabilities,reporting tools, customer management capabilities, employee managementtools, and may integrate with other accounting software.

FIG. 3 depicts an example system 300 that may enable a financialinstitution, for example, to provide network services to its customers.Example system 300 also illustrates examples of merchant systems (e.g.,merchant 107). Merchant systems similar to system 300 may enable afinancial institution and merchant, for example, to grocery budgetingapplication to users of client devices (e.g., client device 302). Clientdevice 302 may be similar to the user device used by account holder 106as described above. Also, network 304 may be similar to network 108 ofFIG. 1.

As shown in FIG. 3, system 300 may include a client device 302, anetwork 304, a front-end controlled domain 306, a back-end controlleddomain 312, and a backend 318. Front-end controlled domain 306 mayinclude one or more load balancers 308 and one or more web servers 310.Back-end controlled domain 312 may include one or more load balancers314 and one or more application servers 316.

Client device 302 may be a network-enabled computer. As referred toherein, a network-enabled computer may include, but is not limited to:e.g., any computer device, or communications device including, e.g., aserver, a network appliance, a personal computer (PC), a workstation, amobile device, a phone, a handheld PC, a personal digital assistant(PDA), a thin client, a fat client, an Internet browser, or otherdevice. The one or more network-enabled computers of the example system300 may execute one or more software applications to enable, forexample, network communications.

Client device 302 also may be a mobile device. For example, a mobiledevice may include an iPhone, iPod, iPad from Apple® or any other mobiledevice running Apple's iOS operating system, any device running Google'sAndroid® operating system, including for example, Google's wearabledevice, Google Glass, any device running Microsoft's Windows® Mobileoperating system, and/or any other smartphone or like wearable mobiledevice.

Network 304 may be one or more of a wireless network, a wired network,or any combination of a wireless network and a wired network. Forexample, network 110 may include one or more of a fiber optics network,a passive optical network, a cable network, an Internet network, asatellite network, a wireless LAN, a Global System for MobileCommunication (GSM), a Personal Communication Service (PCS), a PersonalArea Networks, (PAN), D-AMPS, Wi-Fi, Fixed Wireless Data, IEEE 802.11b,802.15.1, 802.11n, and 802.11g or any other wired or wireless networkfor transmitting and receiving a data signal.

In addition, network 110 may include, without limitation, telephonelines, fiber optics, IEEE Ethernet 902.3, a wide area network (WAN), alocal area network (LAN) or a global network such as the Internet. Also,network 110 may support an Internet network, a wireless communicationnetwork, a cellular network, or the like, or any combination thereof.Network 110 may further include one network, or any number of exampletypes of networks mentioned above, operating as a stand-alone network orin cooperation with each other. Network 110 may utilize one or moreprotocols of one or more network elements to which they arecommunicatively couples. Network 110 may translate to or from otherprotocols to one or more protocols of network devices. Although network110 is depicted as a single network, it should be appreciated thataccording to one or more embodiments, network 110 may comprise aplurality of interconnected networks, such as, for example, theInternet, a service provider's network, a cable television network,corporate networks, and home networks.

Front-end controlled domain 306 may be implemented to provide securityfor backend 318. Load balancer(s) 308 may distribute workloads acrossmultiple computing resources, such as, for example computers, a computercluster, network links, central processing units or disk drives. Invarious embodiments, load balancer(s) 310 may distribute workloadsacross, for example, web server(S) 316 and/or backend 318 systems. Loadbalancing aims to optimize resource use, maximize throughput, minimizeresponse time, and avoid overload of any one of the resources. Usingmultiple components with load balancing instead of a single componentmay increase reliability through redundancy. Load balancing is usuallyprovided by dedicated software or hardware, such as a multilayer switchor a Domain Name System (DNS) server process.

Load balancer(s) 308 may include software that monitoring the port whereexternal clients, such as, for example, client device 302, connect toaccess various services of a financial institution, for example. Loadbalancer(s) 308 may forward requests to one of the application servers316 and/or backend 318 servers, which may then reply to load balancer308. This may allow load balancer(s) 308 to reply to client device 302without client device 302 ever knowing about the internal separation offunctions. It also may prevent client devices from contacting backendservers directly, which may have security benefits by hiding thestructure of the internal network and preventing attacks on backend 318or unrelated services running on other ports, for example.

A variety of scheduling algorithms may be used by load balancer(s) 308to determine which backend server to send a request to. Simplealgorithms may include, for example, random choice or round robin. Loadbalancers 308 also may account for additional factors, such as aserver's reported load, recent response times, up/down status(determined by a monitoring poll of some kind), number of activeconnections, geographic location, capabilities, or how much traffic ithas recently been assigned.

Load balancers 308 may be implemented in hardware and/or software. Loadbalancer(s) 308 may implement numerous features, including, withoutlimitation: asymmetric loading; Priority activation: SSL Offload andAcceleration; Distributed Denial of Service (DDoS) attack protection;HTTP compression; TCP offloading; TCP buffering; direct server return;health checking; HTTP caching; content filtering; HTTP security;priority queuing; rate shaping; content-aware switching; clientauthentication; programmatic traffic manipulation; firewall; intrusionprevention systems.

Web server(s) 310 may include hardware (e.g., one or more computers)and/or software (e.g., one or more applications) that deliver webcontent that can be accessed by, for example a client device (e.g.,client device 302) through a network (e.g., network 304), such as theInternet. In various examples, web servers, may deliver web pages,relating to, for example, online banking applications and the like, toclients (e.g., client device 302). Web server(s) 310 may use, forexample, a hypertext transfer protocol (HTTP or HTTPS) to communicatewith client device 302. The web pages delivered to client device mayinclude, for example, HTML documents, which may include images, stylesheets and scripts in addition to text content.

A user agent, such as, for example, a web browser, web crawler, ornative mobile application, may initiate communication by making arequest for a specific resource using HTTP and web server 310 mayrespond with the content of that resource or an error message if unableto do so. The resource may be, for example a file on stored on backend318. Web server(s) 310 also may enable or facilitate receiving contentfrom client device 302 so client device 302 may be able to, for example,submit web forms, including uploading of files.

Web server(s) also may support server-side scripting using, for example,Active Server Pages (ASP), PHP, or other scripting languages.Accordingly, the behavior of web server(s) 310 can be scripted inseparate files, while the actual server software remains unchanged.

Load balancers 314 may be similar to load balancers 308 as describedabove.

Application server(s) 316 may include hardware and/or software that isdedicated to the efficient execution of procedures (e.g., programs,routines, scripts) for supporting its applied applications. Applicationserver(s) 316 may comprise one or more application server frameworks,including, for example, Java application servers (e.g., Java platform,Enterprise Edition (Java EE), the .NET framework from Microsoft®, PHPapplication servers, and the like). The various application serverframeworks may contain a comprehensive service layer model. Also,application server(s) 316 may act as a set of components accessible to,for example, a financial institution or other entity implementing system300, through an API defined by the platform itself. For Webapplications, these components may be performed in, for example, thesame running environment as web server(s) 310, and application servers316 may support the construction of dynamic pages. Application server(s)316 also may implement services, such as, for example, clustering,fail-over, and load-balancing. In various embodiments, where applicationserver(s) 316 are Java application servers, the web server(s) 316 maybehaves like an extended virtual machine for running applications,transparently handling connections to databases associated with backend318 on one side, and, connections to the Web client (e.g., client device302) on the other.

Backend 318 may include hardware and/or software that enables thebackend services of, for example, a financial institution or otherentity that maintains a distributed system similar to system 300. Forexample, backend 318 may include, a system of record, online bankingapplications, a rewards platform, a payments platform, a lendingplatform, including the various services associated with, for example,auto and home lending platforms, a statement processing platform, one ormore platforms that provide mobile services, one or more platforms thatprovide online services, a card provisioning platform, a general ledgersystem, and the like. Backend 318 may be associated with variousdatabases, including account databases that maintain, for example,customer account information, product databases that maintaininformation about products and services available to customers, contentdatabases that store content associated with, for example, a financialinstitution, and the like. Backend 318 also may be associated with oneor more servers that enable the various services provided by system 300.

In various examples, backend 318 may include similar components asfinancial institution 101. In these examples, backend 318 may enable afinancial institution, along with the various databases, communicationmodules and processors associated therewith to provide a spend memoryrecord to, for example, users of mobile device 302. Backend 318 also mayinclude various backend components that may be associated with amerchant. For example, backend 318 may include systems similar to theretail enterprise system 224 as shown and described above in FIG. 2.

FIG. 4 is a flow chart illustrating a method for providing a spendmemory record to an account holder at his or her mobile device. Themethod 400 shown in FIG. 4 can be executed or otherwise performed by oneor more combinations of various systems. The method 400 as describedbelow may be carried out by the system for providing a spend memoryrecord to an account holder at his or her mobile device as shown inFIGS. 1-3 and 5A-5B, by way of example, and various elements of thatsystem are referenced in explaining the method of FIG. 4. Each blockshown in FIG. 4 represents one or more processes, methods, orsubroutines in the example method 400. Referring to FIG. 4, the examplemethod 400 may begin at block 401.

In block 401, transaction data may be received via a network from amerchant and/or third-party payment processor. The transaction data maybe associated with a financial transaction performed via a financialaccount held by the account holder. The transaction data may beassociated with a financial transaction performed by the account holderat a POS location using a card (e.g., a credit card/debit card) and/oraccount holder's mobile device. The account holder may purchase one ormore goods or services at the POS location, and the resulting expensesmay be charged against the account holder's account.

Transaction data may include, for example, the dollar amount of thetransaction; the transaction location data (e.g., the physical addressof the merchant and/or GPS coordinates associated with the merchantlocation); transaction timestamp data (the date and time of thetransaction); product information; any rewards points earned by accountholder as a result of the transaction; any logos used by the merchant;and any receipts associated with the transaction. In one example, anaccount holder may be traveling on a road trip from Richmond, Va. toDaytona Beach, Fla. During the trip, the account holder may stop inSavannah, Ga. and buy dinner on Aug. 20, 2014 at an Applebee'srestaurant. The transaction data from this purchase may include thetransaction timestamp (Aug. 20, 2014, 6:30:20 PM). The transaction datamay include the transaction location (e.g., the address and/or GPScoordinates associated with Applebee's). Spend memory processor 104 mayreceive the transaction data. Method 400 may proceed to block 402.

In block 402 social data may be retrieved via from a social networkingsite associated with the account holder. Social data may be retrievedvia a network using a social API, for example, that links a financialinstitution with a social networking site. Social data may includephotos and videos that the account holder posts to his social mediaaccounts. Social data can include tweets, pins, tags, check-ins, likes,status updates, comments, profile information, posts, and otherinformation. The account holder may have previously opted-in to receivespend memory records from spend memory processor 104. At that time,social networking site 110 may have created a hashcode to allow spendmemory processor 104 to access social data from the account holder'ssocial media accounts. The hashcode may be associated with one or morelimitations set by the account holder during the opt-in process. Thelimitations may relate to the types of social data that spend memoryprocessor 104 can retrieve. In this example, the account holder may haveset limitations permitting the spend memory processor 104 to retrievephotos and videos from his social media account, along with statusupdates, posts, comments, and likes.

Spend memory processor 104 may provide the hashcode to social networkingsite 110 in order to retrieve social data. Social networking site 110may provide the social data to spend memory processor 104 based on thehashcode and the associated limitations. In this example, while inSavannah, Ga., the account holder may have taken a photo of a locationin the city and posted it to his social media account. The accountholder may have labeled the photo within an album called “Road Trip toDaytona Beach”. The photo may include social location data (e.g., aphysical address and/or GPS coordinates associated with the locationwhere the photo was taken and/or uploaded). The social location data mayhave been added to the photo by the user's mobile device and/or bysocial networking site 110 when the account holder first uploaded thephoto. The account holder may have also posted a status update “Passingthrough Savannah, Ga.” to his social media account. Social networkingsite 110 may provide this social data to spend memory processor 104 inresponse to a request for social data that includes the hashcode. Thesocial data may include social timestamp data (e.g., indicating the dateand time when the social data was created and/or uploaded to socialnetworking site 110). In this example, the social timestamp data for thephoto may be Aug. 20, 2014, 5:50:20 PM, and the social timestamp datafor the status update may be Aug. 20, 2014, 5:30:15 PM.

In various embodiments, during the initial opt-in process, the accountholder may also provide spend memory processor 104 with permission topull data directly from the account holder's mobile device (e.g.,photos, videos, notes, call records). In this example, the accountholder did not provide spend memory processor 104 with this permission,and thus spend memory processor 104 will not pull this data from theaccount holder's mobile device. In various embodiments, local datastored, for example, on a mobile device also may be retrieved in block402. An API may be used in a similar manner as describe above toretrieve the local data. Method 400 may proceed to block 403.

At block 403, social data may be compared to the transactional data.Spend memory processor 104 may compare the received social data,including any retrieved local data, with the received transactionaldata. The comparison may include comparing the transactional locationdata with the social location data. The comparison may include comparingthe transactional timestamp data with the social timestamp data. Spendmemory processor 104 may look for matches based on one or morethresholds, including a location threshold and a time threshold. In thisexample, the location threshold may be social location data that iswithin 10 miles of transactional location data. In this example, thetime threshold may be social timestamp data that is within 12 hours ofthe transactional timestamp data. Spend memory processor 104 maydetermine that the social timestamp data for the photo and the statusupdate is within 12 hours of the transactional timestamp data for theaccount holder's meal at Applebee's. Spend memory processor 104 maydetermine that the social locational data for the status update and thephoto may be within 10 miles of the transactional location data for theaccount holder's meal at Applebee's. Method 400 may proceed to block404.

At block 404, a spend memory record may be prepared based on the matchesdetermined in block 403. In this example, the spend memory record may bea graphical user interface (GUI) that shows each transaction record andthe associated social data. The spend memory record may includetransactional data from the account holder's Applebee's purchase,including the location, date and time, merchant name, purchase amount,and/or a merchant logo. The spend memory record may also include thesocial data, including the photo and the status update. The spend memoryrecord may include text and/or links describing the purchase, based onthe transaction data and the social data (e.g., “bought dinner atApplebee's during your Roadtrip to Daytona Beach”). Method 400 mayproceed to block 405.

At block 405, the spend memory record may be provided to the accountholder's mobile device. The account holder may view the spend memoryrecord on his mobile device using a mobile banking application (such asmobile banking application 103). The user interface for the spend memoryrecord may allow the account holder to customize the display.

It is further noted that the software described herein may be tangiblyembodied in one of more physical media, such as, but not limited to, acompact disc (CD), a digital versatile disc (DVD), a floppy disk, a harddrive, read only memory (ROM), random access memory (RAM), as well asother physical media capable of storing software, or combinationsthereof. Moreover, the figures illustrate various components (e.g.,servers, computers, processors, etc.) separately. The functionsdescribed as being performed at various components may be performed atother components, and the various components bay be combined orseparated. Other modifications also may be made.

In the preceding specification, various preferred embodiments have beendescribed with references to the accompanying drawings. It will,however, be evident that various modifications and changes may be madethereto, and additional embodiments may be implemented, withoutdeparting from the broader scope of the disclosure as set forth in theclaims that follow. The specification and drawings are accordingly to beregarded as an illustrative rather than restrictive sense.

What is claimed is:
 1. A system comprising: one or more processors; atransceiver to send and receive one or more of wired and wirelesscommunications; a screen to display a first graphical user interface(GUI) and a second GUI, the first GUI and the second GUI associated witha mobile banking application; memory, comprising the mobile bankingapplication, and in communication with the transceiver, the one or moreprocessors, and the screen, the memory including instructions that, whenexecuted, cause the one or more processors to: display, on the firstGUI: a list of one or more financial transactions; transaction dataassociated with the one or more financial transactions; and one or morefirst inputs, each first input associated with one of the one or morefinancial transactions; receive, at the first GUI, a selection of afirst input associated with a first financial transaction of the one ormore financial transactions; send, with the transceiver, a request for aspend memory record associated with the first financial transaction to aspend memory processor associated with a financial institution; receive,from a financial account holder via the mobile banking application, oneor more second inputs to create one or more permissions, wherein eachpermission enables the spend memory processor to retrieve one or moretypes of social data from a social media account of the financialaccount holder; receive, at the transceiver, a response from the spendmemory processor comprising the spend memory record, the spend memoryrecord comprising the one or more types of social data associated withthe first financial transaction; display, on the second GUI, the spendmemory record associated with the first financial transaction, and thetransaction data associated with the first financial transaction; andreceive, at the second GUI, a confirmation of the first financialtransaction from the financial account holder.
 2. The system of claim 1,wherein the transaction data comprises one or more of a transactionamount, a transaction timestamp, a transaction location, productinformation, or a merchant logo.
 3. The system of claim 1, wherein thesocial data comprises one or more of a social timestamp associated witha social publication on a social network or a social location associatedwith the social publication, the social publication comprises one ormore of a photo, a video, or a social media post.
 4. The system of claim1, wherein the spend memory record further comprises one or more of: anaccount number, a merchant name associated with the first financialtransaction, or a text description of the first financial transaction.5. The system of claim 1, wherein the instructions further cause the oneor more processors to: display, on the second GUI, the spend memoryrecord associated with the first financial transaction; and one or morethird inputs associated with the spend memory record, each third inputassociated with a respective portion of the social data; and receive, atthe second GUI, a selection of a third input of the one or more thirdinputs, wherein the selection of the third input comprises aconfirmation that a first portion of the social data is associated withthe first financial transaction.
 6. The system of claim 1, wherein theone or more permissions further enable the spend memory processor toretrieve local data from a mobile device; and wherein the local datacomprises one or more of a device timestamp, a device location, a photo,a video, a call log, or a text message.
 7. A system comprising: one ormore processors; a transceiver to send and receive one or more of wiredand wireless communications; a screen to display a first graphical userinterface (GUI) and a second GUI, the first GUI and the second GUIassociated with a mobile banking application; memory, comprising themobile banking application and local data, and in communication with thetransceiver, the one or more processors, and the screen, the memoryincluding one or more instructions that, when executed, cause the one ormore processors to: display, at the first GUI: a list of one or morefinancial transactions; transaction data associated with the one or morefinancial transactions; and one or more first inputs, each first inputassociated with one of the one or more financial transactions; receive,at the first GUI, a selection of a first input associated with a firstfinancial transaction of the one or more financial transactions; send,with the transceiver, a request for a spend memory record associatedwith the first financial transaction to a spend memory processorassociated with a financial institution; receive, from a financialaccount holder via the mobile banking application, one or more secondinputs to create one or more opt-in permissions, wherein each permissionenables the spend memory processor to retrieve one or more types oflocal data from a mobile device; receive, at the transceiver, a responsefrom the spend memory processor comprising the spend memory record, thespend memory record comprising the one or more types of local dataassociated with the first financial transaction; display, on the secondGUI, the spend memory record associated with the first financialtransaction, and the transaction data associated with the firstfinancial transaction; and query the financial account holder to confirmthe first financial transaction; wherein the transaction data comprisesone or more of a transaction amount, a transaction timestamp, atransaction location, product information, or a merchant logo; andwherein the local data comprises one or more of a device timestamp, adevice location, a photo, a video, a call log, or a text message.
 8. Thesystem of claim 7, wherein the spend memory record further comprises oneor more of an account number, a merchant name, or a text description ofthe first financial transaction.
 9. The system of claim 7, wherein theinstructions further cause the one or more processors to: display, onthe second GUI, the spend memory record associated with the firstfinancial transaction and one or more third inputs associated with thespend memory record, each third input associated with a respectiveportion of the transaction data; and receive, at the second GUI, aselection of a third input of the one or more third inputs, wherein theselection of the third input comprises a confirmation of the firstfinancial transaction.
 10. The system of claim 7, wherein theinstructions further cause the one or more processors to: display, onthe second GUI, the spend memory record associated with the firstfinancial transaction, and one or more third inputs associated with thespend memory record, each of the one or more third inputs associatedwith a respective portion of the local data; and receive, at the secondGUI, a selection of a third input of the one or more third inputs,wherein the selection of the third input comprises a confirmation that afirst portion of the local data is associated with the first financialtransaction.
 11. The system of claim 7, wherein the one or more opt-inpermissions further enable the spend memory processor to retrieve socialdata from a user's social media account; and wherein the social datacomprises one or more of a social timestamp associated with a socialpublication on a social network or a social location associated with thesocial publication; and wherein the social publication comprises one ormore of a photo, a video, or a social media post.
 12. A method,comprising: displaying, on a screen of a mobile device, a firstgraphical user interface (GUI) associated with a mobile bankingapplication, the first GUI including at least: a list of one or morefinancial transactions; transaction data associated with the one or morefinancial transactions; and one or more first inputs, each first inputassociated with one of the one or more financial transactions;receiving, at the first GUI, a selection of a first input associatedwith a first financial transaction of the one or more financialtransactions; sending, with a transceiver of the mobile device, arequest for a spend memory record associated with the first financialtransaction to a spend memory processor, the spend memory recordcomprising one or more of social data associated with the firstfinancial transaction, an account number associated with the firstfinancial transaction, a merchant name associated with the firstfinancial transaction, or a text description associated with the firstfinancial transaction; receiving from a user of the mobile device viathe mobile banking application, one or more second inputs to create oneor more permissions, wherein each permission enables the spend memoryprocessor to retrieve one or more types of social data from a socialmedia account of the user; receiving, at the transceiver, a responsefrom the spend memory processor, the response comprising the spendmemory record; displaying, on the screen, a second GUI associated withthe mobile banking application, the second GUI comprising: the spendmemory record; the transaction data associated with the first financialtransaction; and one or more third inputs associated with the firstfinancial transaction; and receiving, at the second GUI, a third inputof the one or more third inputs confirming the first financialtransaction.
 13. The method of claim 12, wherein the one or morepermissions further enable the spend memory processor to retrieve localdata on the mobile device, the local data comprising one or more of adevice timestamp, a device location, a photo, a video, a call log or atext message.
 14. The method of claim 12, further comprising:displaying, on the second GUI, the spend memory record associated withthe first financial transaction, and one or more fourth inputsassociated with the spend memory record, each of the one or more fourthinputs associated with a respective portion of the social data; andreceiving, at the second GUI, a selection of a fourth input of the oneor more fourth inputs, wherein the selection of the fourth inputcomprises a confirmation that a first portion of the social data isassociated with the first financial transaction.
 15. The method of claim12, wherein the transaction data comprises one or more of a transactionamount, a transaction timestamp, a transaction location, productinformation, or a merchant logo.
 16. The method of claim 12, wherein thesocial data comprises one or more of a social timestamp associated witha social publication or a social location associated with the socialpublication on a social network, the social publication comprising oneor more of a photo, a video or a social media post.